CAN-LIN SBC Click
CAN-LIN SBC Click demo application is developed using the NECTO Studio, ensuring compatibility with mikroSDK's open-source libraries and tools. Designed for plug-and-play implementation and testing, the demo is fully compatible with all development, starter, and mikromedia boards featuring a mikroBUS™ socket.
Click Library
- Author : Stefan Filipovic
- Date : Jan 2025.
- Type : SPI type
Software Support
Example Description
This example demonstrates the use of an CAN-LIN SBC Click board by showing the communication between the two Click boards.
Example Libraries
- MikroSDK.Board
- MikroSDK.Log
- Click.CANLINSBC
Example Key Functions
- canlinsbc_cfg_setup Config Object Initialization function.
void canlinsbc_cfg_setup(canlinsbc_cfg_t *cfg)
CAN-LIN SBC configuration object setup function.
CAN-LIN SBC Click configuration object.
Definition canlinsbc.h:276
- canlinsbc_init Initialization function.
err_t canlinsbc_init(canlinsbc_t *ctx, canlinsbc_cfg_t *cfg)
CAN-LIN SBC initialization function.
CAN-LIN SBC Click context object.
Definition canlinsbc.h:249
- canlinsbc_default_cfg Click Default Configuration function.
err_t canlinsbc_default_cfg(canlinsbc_t *ctx)
CAN-LIN SBC default configuration function.
- canlinsbc_generic_write This function writes a specified number of bytes to the CAN LIN SBC device using UART communication.
err_t canlinsbc_generic_write(canlinsbc_t *ctx, uint8_t *data_in, uint16_t len)
CAN LIN SBC generic write function.
- canlinsbc_generic_read This function reads a specified number of bytes from the CAN LIN SBC device using UART communication.
err_t canlinsbc_generic_read(canlinsbc_t *ctx, uint8_t *data_out, uint16_t len)
CAN LIN SBC generic read function.
Application Init
Initializes the driver and logger, and performs the Click default configuration.
{
log_cfg_t log_cfg;
LOG_MAP_USB_UART( log_cfg );
log_init( &logger, &log_cfg );
log_info( &logger, " Application Init " );
if ( SPI_MASTER_ERROR ==
canlinsbc_init( &canlinsbc, &canlinsbc_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
#ifdef DEMO_APP_TRANSMITTER
log_printf( &logger, " Application Mode: Transmitter\r\n" );
#else
log_printf( &logger, " Application Mode: Receiver\r\n" );
#endif
log_info( &logger, " Application Task " );
}
@ CANLINSBC_ERROR
Definition canlinsbc.h:309
#define CANLINSBC_MAP_MIKROBUS(cfg, mikrobus)
MikroBUS pin mapping.
Definition canlinsbc.h:230
void application_init(void)
Definition main.c:38
Application Task
Depending on the selected application mode, it reads all the received data or sends the desired message once per second.
{
#ifdef DEMO_APP_TRANSMITTER
Delay_ms( 1000 );
#else
uint8_t rx_data = 0;
{
log_printf( &logger, "%c", rx_data );
}
#endif
}
#define DEMO_TEXT_MESSAGE
Definition main.c:33
void application_task(void)
Definition main.c:80
Note
Ensure the two Click boards are connected properly using an RS232 cable and a 12V external power supply is provided to the VEXT pin.
Application Output
This Click board can be interfaced and monitored in two ways:
- Application Output - Use the "Application Output" window in Debug mode for real-time data monitoring. Set it up properly by following this tutorial.
- UART Terminal - Monitor data via the UART Terminal using a USB to UART converter. For detailed instructions, check out this tutorial.
Additional Notes and Information
The complete application code and a ready-to-use project are available through the NECTO Studio Package Manager for direct installation in the NECTO Studio. The application code can also be found on the MIKROE GitHub account.